home *** CD-ROM | disk | FTP | other *** search
- Path: ar.ar.com.au!not-for-mail
- From: storm@ar.ar.com.au (Storm)
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: OS features
- Date: 23 Jan 1996 13:26:59 +1100
- Organization: I need to put my ORGANIZATION here.
- Distribution: inet
- Message-ID: <4e1h1j$aca@ar.ar.com.au>
- References: <92747544038@PAPA.NORTH.DE> <4b3h9s$1st@alterdial.UU.NET>
- NNTP-Posting-Host: ar.ar.com.au
- X-Newsreader: TIN [UNIX 1.3 941216BETA PL0]
-
- Janne Jalkanen (Janne.Jalkanen@hut.fi) wrote:
-
- : Something like MEMF_PUBLIC, MEMF_PROTECTED and MEMF_PRIVATE? I have
- : been toying around with a similar idea. Code space would be allocated
- : from protected memory space, so that crazed programs could not write
- : over existing code (and self-modifying code works badly anyway).
-
- What about programs that store data in a code hunk so it can be addressed
- PC-relative? I have no idea how common this is but it could break many
- programs if CODE hunks are write protected..
-
- Self-modifying code would not be a problem really - I don't think many
- people use it in programs that don't kill the system anyway.. :-)
-
- -- ______________________________
- \_/ "\/\/\__"\/ "\/ "\/\__"\_/
- Storm / Cydonia / / / / / / / / / / / / ' / Packing class
- / /\/> / / / / / / / / / /__ & kicking arse!
- (coder) \__/ \_/\__/\__/\/\/\/\/\/ \/
-